Search Results

Your search for 130 returned the following results.

Prerequisites

I have several posts regarding CISCO 8000 software installation shown below:

The most important is to understand how to use a local repository or remote repository.

This article also applies to other products using XR7, such as some NCS540.

SMU install (Use local repository)

Copy all SMU file to the local folder, in this case, i create a folder named “repo” under harddisk:

[node0_RP0_CPU0:/harddisk:/repo]$ls
8000-7.3.15.CSCvw58830.tar  8000-7.3.15.CSCvy35867.tar
8000-7.3.15.CSCvx48017.tar  8000-7.3.15.CSCvy42027.tar
8000-7.3.15.CSCvx50864.tar  8000-7.3.15.CSCvy43997.tar
8000-7.3.15.CSCvx68887.tar  8000-7.3.15.CSCvy52710.tar
8000-7.3.15.CSCvx76463.tar  8000-7.3.15.CSCvy53516.tar
8000-7.3.15.CSCvx84404.tar  8000-7.3.15.CSCvy55726.tar
8000-7.3.15.CSCvx99992.tar  8000-7.3.15.CSCvy61939.tar
8000-7.3.15.CSCvy06576.tar  8000-7.3.15.CSCvy66996.tar
8000-7.3.15.CSCvy12145.tar  8000-7.3.15.CSCvy67283.tar
8000-7.3.15.CSCvy14896.tar  8000-7.3.15.CSCvy72415.tar
8000-7.3.15.CSCvy16526.tar  8000-7.3.15.CSCvy73299.tar
8000-7.3.15.CSCvy16725.tar  8000-7.3.15.CSCvy77182.tar
8000-7.3.15.CSCvy17864.tar  8000-7.3.15.CSCvz04661.tar
8000-7.3.15.CSCvy24941.tar  8000-7.3.15.CSCvz25325.tar
8000-7.3.15.CSCvy26732.tar  8000-7.3.15.CSCvz45349.tar
8000-7.3.15.CSCvy33251.tar  8000-7.3.15.CSCvz67583.tar
8000-7.3.15.CSCvy33657.tar

then try unzip all the smu file buy use two simple shell script:

[node0_RP0_CPU0:/harddisk:/repo]$for tar in *.tar; do tar -xvf $tar; done
8000-7.3.15.CSCvw58830.txt
8000-x86_64-7.3.15-CSCvw58830.tgz
8000-7.3.15.CSCvx48017.txt
8000-x86_64-7.3.15-CSCvx48017.tgz
8000-7.3.15.CSCvx50864.txt
8000-x86_64-7.3.15-CSCvx50864.tgz

[node0_RP0_CPU0:/harddisk:/repo]$for tar in *.tgz; do tar -xvf $tar; done
8000-x86_64-7.3.15-CSCvw58830/
8000-x86_64-7.3.15-CSCvw58830/xr-rpl-8608-rp1-7.3.15v1.0.1-1.x86_64.rpm
8000-x86_64-7.3.15-CSCvw58830/xr-rpl-88-lc0-34h14fh-7.3.15v1.0.1-1.x86_64.rpm
8000-x86_64-7.3.15-CSCvw58830/xr-rpl-8102-64h-7.3.15v1.0.1-1.x86_64.rpm
8000-x86_64-7.3.15-CSCvw58830/primary.xml.gz
8000-x86_64-7.3.15-CSCvw58830/xr-rpl-8201-7.3.15v1.0.1-1.x86_64.rpm
8000-x86_64-7.3.15-CSCvw58830/xr-rpl-d17f630e9aaec8a3-7.3.15v1.0.1-1.x86_64.rpm
8000-x86_64-7.3.15-CSCvw58830/xr-rpl-7.3.15v1.0.1-1.x86_64.rpm

Config the local repository with the path “file:///harddisk:/repo/”

RP/0/RP0/CPU0:8201-01#conf 
Thu Oct  7 06:36:45.111 UTC
RP/0/RP0/CPU0:8201-01(config)#
RP/0/RP0/CPU0:8201-01(config)#
RP/0/RP0/CPU0:8201-01(config)#install 
RP/0/RP0/CPU0:8201-01(config-install)#no repository remo-repo
RP/0/RP0/CPU0:8201-01(config-install)#
RP/0/RP0/CPU0:8201-01(config-install)#repository local-repo
RP/0/RP0/CPU0:8201-01(config-repository)#url file:///harddisk:/repo/
RP/0/RP0/CPU0:8201-01(config-repository)#commit 
Thu Oct  7 06:38:04.997 UTC
RP/0/RP0/CPU0:8201-01(config-repository)#

We have two command to check the SMU in the local repository:

RP/0/RP0/CPU0:MXC.TAC.L.08-8201-01#show install available 
Thu Oct  7 06:38:10.721 UTC
Trying to access repositories...

Package                                              Architecture                         Version Repository                          Cached
---------------------------------------------------- ---------------- --------------------------- ----------------------------------- ------
xr-8000-bmc                                          x86_64                        7.3.15v1.0.1-1 local-repo                                
xr-8000-bmc                                          x86_64                        7.3.15v1.0.2-1 local-repo                                
xr-8000-bmc                                          x86_64                        7.3.15v1.0.3-1 local-repo                                
xr-8000-bmc                                          x86_64                        7.3.15v1.0.4-1 local-repo                                
xr-8000-core                                         x86_64                        7.3.15v1.0.1-1 local-repo                                

RP/0/RP0/CPU0:MXC.TAC.L.08-8201-01#show install fixes available                
Thu Oct  7 06:38:31.839 UTC
Trying to access repositories...

Available Fixes (count: 33):
Bug Id      Packages                                                    Repository                               Cached
----------- ----------------------------------------------------------- ---------------------------------------- ------
CSCvw58830  xr-rpl-7.3.15v1.0.1-1                                       local-repo                                     
CSCvx48017  xr-security-7.3.15v1.0.2-1                                  local-repo                                     
CSCvx50864  xr-bundles-7.3.15v1.0.1-1                                   local-repo                                     
CSCvx68887  xr-8000-core-7.3.15v1.0.3-1                                 local-repo                                     
            xr-8000-core-7.3.15v1.0.4-1                                 local-repo                                     
            xr-8000-core-7.3.15v1.0.5-1                                 local-repo                                     
            xr-spi-core-7.3.15v1.0.1-1                                  local-repo                                     
            xr-spi-core-7.3.15v1.0.2-1                                  local-repo                                     

We have there way to install the smu we want:

install package add cisco-CSCab12345install a special SMU
install package upgrade xr-coreinstall cups of smu to fix special component
install package upgradeinstall all the smu under your repository

Here is an example to install all the smu under repository:

RP/0/RP0/CPU0:MXC.TAC.L.08-8201-01#install package upgrade 
Thu Oct  7 06:38:50.536 UTC
Install upgrade operation 38.1.1 has started
Install operation will continue in the background
RP/0/RP0/CPU0:MXC.TAC.L.08-8201-01#show install request  
Thu Oct  7 06:39:01.467 UTC

User request: install package upgrade
Operation ID: 38.1.1
State:        In progress since 2021-10-07 06:38:50 UTC

Current activity:    Begin transaction
Next activity:       Begin atomic operation
Time started:        2021-10-07 06:38:54

No per-location information.

RP/0/RP0/CPU0:MXC.TAC.L.08-8201-01#show install request 
Thu Oct  7 06:41:43.859 UTC

User request: install package upgrade
Operation ID: 38.1.1
State:        In progress since 2021-10-07 06:38:50 UTC

Current activity:    Package add or other package operation
Next activity:       Await user input
Time started:        2021-10-07 06:40:45
Timeout in:          39m 0s
Locations responded: 0/1

Location          Packaging operation stage Notification Phase Clients responded
----------------- ------------------------- ------------------ -----------------
0/RP0/CPU0        Package operations        None in progress                 N/A
RP/0/RP0/CPU0:MXC.TAC.L.08-8201-01#
RP/0/RP0/CPU0:MXC.TAC.L.08-8201-01#
RP/0/RP0/CPU0:MXC.TAC.L.08-8201-01#
RP/0/RP0/CPU0:MXC.TAC.L.08-8201-01#show install request 
Thu Oct  7 06:43:07.645 UTC

User request: install package upgrade
Operation ID: 38.1.1
State:        Success since 2021-10-07 06:42:51 UTC

Current activity:    Await user input
Time started:        2021-10-07 06:42:52

The following actions are available:
    install package add
    install package remove
    install package upgrade
    install package downgrade
    install package replace
    install package rollback
    install package abort latest
    install package abort all-since-apply
    install apply reload                                    


SMU apply and commit

after install, use “install apply” to active the SMU , this action may need reload the router.

RP/0/RP0/CPU0:MXC.TAC.L.08-8201-01#install apply synchronous         ins
Thu Oct  7 06:46:54.637 UTC
Once the packaging dependencies have been determined, the install operation may have to reload the system.
If you want more control of the operation, then explicitly use 'install apply restart' or 'install apply reload' as reported by 'show install request'.
Continue? [yes/no]:[yes] yes
Starting:
  install apply reload
Atomic change 38.1
Press Ctrl-C to return to the exec prompt. This will not cancel the install operation

Current activity: Initializing
Current activity: Apply by reloadRP/0/RP0/CPU0:Oct  7 06:47:01.971 UTC: instorch[154]: %INFRA-INSTALL-2-SYSTEM_RELOAD : As part of an install operation, a full system reload will take place in order to apply the installed software. 
 .
Preparing system for backup. This may take a few minutes especially for large configurations.
        Status report: node0_RP0_CPU0: START TO BACKUP 
        Status report: node0_RP0_CPU0: BACKUP HAS COMPLETED SUCCESSFULLY 
[Done]
......[13068.510009] do_IRQ: 0.196 No irq handler for vector


Don’t forgot “install commit” after router reload:

RP/0/RP0/CPU0:MXC.TAC.L.08-8201-01#install commit 
Thu Oct  7 06:55:51.414 UTC
Install commit operation 38 has started
Install operation will continue in the background

comments by ‘zhihua’

对于ASR9000来说 :
“show interfaces” and “show policy-map interfaces” show L2 frame size.
“show interfaces” does not include FCS bytes, but “show policy-map interfaces” includes FCS bytes(SIP700是个例外)

L1 frame size 和 L2 frame size

如上图就是一个以太网帧的物理层具体所包含的内容。

  • Preamble: 前同步码 7 bytes
  • SFD: start frame delimiter 1 byte 帧开始定界符
  • Dst MAC: 6 bytes
  • Src MAC: 6 bytes
  • EtherType: 2 bytes
  • FCS(CRC): 4 bytes
Read the rest of this entry »

最近尝试了下使用Golden ISO升级了下设备,发现其比使用官方提供的mini的ISO镜像更方便,时间更短,属实是太方便了。

什么是Golden ISO呢,GISO属于自定义的镜像文件,可以选择性的将mini iso + option rpm + smu + config file 等定制成一个镜像文件,这样我们在升级的时候只需要安装一个文件,可以省略之前很多很多的步骤。

GISO分为以下两种:

  • Optimised GISO (目前只能由官方提供)
  • Non-optimised GISO (使用github上public的python 脚本自己自定义)

Non-optimised GISO的缺点:

如果使用python脚本自定义的GISO,无法用于PXE安装,即使PXE安装了也只会成功安装mini iso,其它的自定义的oprion rpm/config 文件不会被加载。文章最后会说一下如何解决这个问题。

本文主要来介绍,如何使用Github上的脚本自己在本地定制化GISO文件。

Read the rest of this entry »

ASR9K

CPU

这张图涵盖了ASR9000 全系列板卡的架构以及使用的芯片, 其中最右边一列为CPU的类型; 可以看到最初一代和二代板卡使用的都是PowerPC的处理器, PowerPC采用的都是32位的指令集, 这也是为什么这两代板卡没法跑在最新的64位XR系统上的原因。最新的三代采用的都是Intel的处理器, 使用以下命令我们可以查看板卡处理器(CPU)的类型:

0/0/CPU0 使用的是四核E500型号的CPU, 0/6/CPU0 采用的是8核英特尔686。

Read the rest of this entry »

Step 1: Reload Cisco 8000 and Config PXE

  1. Reload chassis
  2. Enter ESC to BIOS, Select “Boot Manager” then IPXE
iPXE initialising devices...ok
 
 
 
iPXE 1.0.0+ (b965) -- Open Source Network Boot Firmware -- http://ipxe.org
Features: DNS HTTP HTTPS TFTP EFI ISO9660_grub Menu
iPXE>                             
iPXE> ifopen net0
iPXE>
iPXE>
iPXE> ifstat     
net0: 08:4f:a9:5c:fb:c9 using i210 on PCI02:00.0 (open)
  [Link:up, TX:0 TXE:0 RX:10 RXE:3]
  [RXE: 1 x "The socket is not connected (http://ipxe.org/380f6093)"]
  [RXE: 1 x "Error 0x440e6083 (http://ipxe.org/440e6083)"]
  [RXE: 1 x "Operation not supported (http://ipxe.org/3c086083)"]
net1: 00:a0:c9:00:00:00 using x557 on PCI04:00.0 (closed)
  [Link:down, TX:0 TXE:0 RX:0 RXE:0]
  [Link status: Down (http://ipxe.org/38086193)]
net2: 08:4f:a9:5c:fb:ca using x557 on PCI04:00.1 (closed)
  [Link:down, TX:0 TXE:0 RX:0 RXE:0]
  [Link status: Down (http://ipxe.org/38086193)]
iPXE>
iPXE> set net0/ip 10.75.49.7
iPXE> set net0/netmask 255.255.255.0
iPXE> set net0/gateway 10.75.49.1
iPXE> ifopen net0

3. BOOT the ONIE image.

iPXE> boot tftp://10.76.76.160/onie-recovery-x86_64-cisco_8000-r0.efi64.pxe
tftp://10.76.76.160/onie-recovery-x86_64-cisco_8000-r0.efi64.pxe... 94%
                                                                    ok 
Read the rest of this entry »

BGP Flow Specification功能是一种用于防止DoS(Denial of Service)/DDoS(Distributed Denial of Service)攻击的方法,可以提高网络安全性和可用性。其实现方式为 BGP FS controller 通过BGP下发特定的规则给BGP FS client, BGP FS client收到后按照该规则对特定流进行redirect/remark/drop/rate limit。

Read the rest of this entry »

在之前的文章里, 介绍install command升级Cisco 8000的方法, 这篇文章记录下使用PXE bring up一台新的Cisco 8000的过程

  1. Reload chassis
  2. 按ESC进入BIOS, 选择Boot Manager —– PXE
Read the rest of this entry »
reoptimize timers delay cleanup 60
reoptimize timers delay installation 60
reoptimize timers delay path-protection 50 


Install delay:
How much time the head end waits before it "activates" the reoptimized LSP after receiving the RESV. This gives some time to mid/tail nodes to program their fowardng.

Cleanup delay:
How much time the "old" LSP is kept around after the new reoptimize LSP has been installed. This makes sure there's no longer and traffic flowing over the "old" LSP before tearing it down

Path-protection 
Delays the time between path protection switchover event and tunnel reoptimization. 

//default values:

cleanup delay: 20
installation delay: 20
path-protection: 180 
Read the rest of this entry »

Tags:

More results »